Description

This PR fixes the issue when allocations view is not updated when switching region. This leads to user seeing incorrect data and further errors when they try to interact with it - for eg. trying to access a job not existing in the newly switched region.

The changes in the PR are as below:

• The region change was not being detected correctly in the application router when comparing active region and region from query params
• Updated region switcher to not set the active region and let it be updated by application router after comparing with query params
• Removed global store.unloadAll which was causing rendering errors and replaced it with route.refresh to reload active route models for the selected region
• Updated child detail routes (job and allocation) to explicitly reload related region data, avoiding reuse of stale cache after switching regions
• Added new tests to verify loading of jobs and job detail data with the selected region
• Updated failing tests to reflect the change in logic for explicit loading job and job detail data

Testing & Reproduction steps

To reproduce the issue, set up Nomad instances with two regions and deploy a job to the federated cluster.

• Start instance for region 1

bin/nomad agent -dev -config=india-dev.hcl

• Start instance for region 2

bin/nomad agent -dev -config=us-dev.hcl

• Join the instances and deploy a sample job in both instances

bin/nomad server join -address=http://127.0.0.1:5646 127.0.0.1:4648
bin/nomad job run -region=india minimal-job.nomad
bin/nomad job run -region=us minimal-job.nomad

• Launch UI and navigate to jobs view http://localhost:4646/ui/jobs/example
• Switch between regions and observe the recent allocations data does not refresh
• Also click on an allocation id after switching initial region to observe object not found error

To verify the fix, please make another build with the PR branch and repeat the above steps

make dev-ui

You should see updated data for relevant region without any errors

Including the files mentioned above for reference:
NMD917-test-files.zip

Links

JIRA

Contributor Checklist

• Changelog Entry If this PR changes user-facing behavior, please generate and add a
  changelog entry using the make cl command.
• Testing Please add tests to cover any new functionality or to demonstrate bug fixes and
  ensure regressions will be caught.
• Documentation If the change impacts user-facing functionality such as the CLI, API, UI,
  and job configuration, please update the Nomad product documentation, which is stored in the
  web-unified-docs repo. Refer to the web-unified-docs contributor guide for docs guidelines.
  Please also consider whether the change requires notes within the upgrade
  guide. If you would like help with the docs, tag the nomad-docs team in this PR.

Reviewer Checklist

• Backport Labels Please add the correct backport labels as described by the internal
  backporting document.
• Commit Type Ensure the correct merge method is selected which should be "squash and merge"
  in the majority of situations. The main exceptions are long-lived feature branches or merges where
  history should be preserved.
• Enterprise PRs If this is an enterprise only PR, please add any required changelog entry
  within the public repository.

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.